Easier plugin debugging by noting source filename of internal exceptions#1958
Closed
Zac-HD wants to merge 1 commit intoPyCQA:mainfrom
Closed
Easier plugin debugging by noting source filename of internal exceptions#1958Zac-HD wants to merge 1 commit intoPyCQA:mainfrom
Zac-HD wants to merge 1 commit intoPyCQA:mainfrom
Conversation
Member
|
for debugging I'd recommend setting a breakpoint instead! |
Member
Author
|
What's the downside of this? Of course I can pull out a debugger out if I need to, and get the raw invocation instead of going via whatever tooling, but adding a note means I don't even need to because the file responsible is printed right there when I first discover something is wrong. |
Member
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I patched this in while trying to track down where in a rather large codebase python-trio/flake8-async#322 was triggered, and then thought that it was useful enough and had so little downside that I should open this PR 🙂